0x631998e91476DA5B870D741192fc5Cbc55F5a52E
on the Polygon network. Second, let’s build the metadata lookup endpoint to query Skyweaver’s contract
for token ID 20
:
Request
Response:
20
, 21
, and 22
in a single batched request.
Feel free to try tweaking the metadata.sequence.app URL above for your own contract, or another popular
project to see how the responses come back. You can change the network to one of our supported networks
and specify any contract and/or token id.
In addition to easily querying token-level metadata like in the above example, you can also query contract-level metadata.
Contract-level metadata provides you more information about a contract address such as a name, contract type, logo, and description.
Simply change the metadata URL above to just query the contract address
and see result:
<network>
must be one of the Chain ID
or Chain Handle
of the supported networks.
Fetch contract-level metadata:
GetTokenMetadata
- fetch token metadata of ERC721 or ERC1155 tokens from a single contractGetTokenMetadataBatch
- fetch token metadata of ERC721 or ERC1155 token from a batch of contractsGetContractInfo
- fetch contract metadata of an ERC20, ERC721 or ERC1155 contract addressGetContractInfoBatch
- fetch contract metadata of a batch of ERC20, ERC721 or ERC1155 contract addressesSearchContracts
- fetch contract metadata info based on search criteria for ERC20, ERC721, and ERC1155 tokens